Micron Document




Object-oriented user interface
part 7/8 · 11.3 KB total
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
The CUA guidelines stated that 'In an object-oriented user interface, the objects that a user works with do not necessarily correspond to the objects or modules of code, that a programmer used to create the product.'cite-ref-cua-7-1[7] The basic design methods described in CUA were refined further into the OVIDcite-ref-ovid-9-0[9] method which used UML to model the interface.

Mark van Harmelen states that 'Object-oriented user interface design does not require designers to take an object-oriented view of the problem from the beginning of the project. Furthermore, even if designers take an object-oriented perspective throughout, they will benefit from focusing separately on the object model and the object-oriented user interface design.'cite-ref-harmelen-10-0[10]

By contrast, the naked objects pattern is an approach to the design of applications that, at least in its naive form, enforces a direct correspondence between the objects represented in the OOUI and the underlying domain objects, auto-generating the former from the latter.cite-ref-pawson-11-0[11]

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────